REVERT: A Monitor Generation Tool for Real-Time Systems

IEEE Real-Time Systems Symposium (RTSS 2016). 29, Nov to 2, Dec, 2016, RTSS@Work. Porto, Portugal.We present REVERT (which stands for RuntimE VErification for Real-Time systems), a new tool to generate monitors for real-time systems. REVERT takes specifications written in a new Domain Specific Language (DSL) and automatically generates monitors under the form of complete timed deterministic finite automata (DFA). The generated timed DFA can later be used to generate code that can eventually be integrated within the monitored system.info:eu-repo/semantics/publishedVersio

REVERT: Runtime Verification for Real-Time Systems Conference Paper Sangeeth Kochanthara REVERT: Runtime Verification for Real-Time Systems REVERT: Runtime Verification for Real-Time Systems

Abstract Real-time systems are becoming more complex andopen, thus increasing their development and verification costs.Although several static verification tools have been proposedover the last decades, they suffer from scalability and precisionproblems. As a result, the tools fail to cover all the necessarysafety properties for realistic real-time applications involving alarge number of components and tasks. Runtime verification is aformal technique that verifies properties during system executionwith the support of monitors. The monitors are generatedfrom formal languages using correct-by-construction generationmethods. Runtime verification can thus be used as a complementor replacement for static verification approaches. The currentstate-of-the-art tools either do not have notion of time, or sufferfrom the potential blowup of states at run-time. In this paper,we propose REVERT, a framework developed with a focus onthe verification of functional and non-functional properties withtiming constraints. The contribution of this work is twofold: (i) adomain-specific specification language allowing the definition ofrequirements for real-time applications; (ii) a novel mechanism togenerate monitors, with statespace and time guarantees, capableof identifying and reacting to timing properties defined with theproposed specification language. Rahul Purandare IIIT-Delhi, India Abstract-Real-time systems are becoming more complex and open, thus increasing their development and verification costs. Although several static verification tools have been proposed over the last decades, they suffer from scalability and precision problems. As a result, the tools fail to cover all the necessary safety properties for realistic real-time applications involving a large number of components and tasks. Runtime verification is a formal technique that verifies properties during system execution with the support of monitors. The monitors are generated from formal languages using correct-by-construction generation methods. Runtime verification can thus be used as a complement or replacement for static verification approaches. The current state-of-the-art tools either do not have notion of time, or suffer from the potential blowup of states at run-time. In this paper, we propose REVERT, a framework developed with a focus on the verification of functional and non-functional properties with timing constraints. The contribution of this work is twofold: (i) a domain-specific specification language allowing the definition of requirements for real-time applications; (ii) a novel mechanism to generate monitors, with state-space and time guarantees, capable of identifying and reacting to timing properties defined with the proposed specification language

REVERT: Runtime Verification for Real-Time Systems

Work in Progress Session, IEEE Real-Time Systems Symposium (RTSS 2016). 29, Nov to 2, Dec, 2016. Porto, Portugal.Real-time systems are becoming more complex and open, thus increasing their development and verification costs. Although several static verification tools have been proposed over the last decades, they suffer from scalability and precision problems. As a result, the tools fail to cover all the necessary safety properties for realistic real-time applications involving a large number of components and tasks. Runtime verification is a formal technique that verifies properties during system execution with the support of monitors. The monitors are generated from formal languages using correct-by-construction generation methods. Runtime verification can thus be used as a complement or replacement for static verification approaches. The current state-of-the-art tools either do not have notion of time, or suffer from the potential blowup of states at run-time. In this paper, we propose REVERT, a framework developed with a focus on the verification of functional and non-functional properties with timing constraints. The contribution of this work is twofold: (i) a domain-specific specification language allowing the definition of requirements for real-time applications; (ii) a novel mechanism to generate monitors, with state-space and time guarantees, capable of identifying and reacting to timing properties defined with the proposed specification language.info:eu-repo/semantics/publishedVersio

REVERT: Runtime Verification for Real-Time Systems

Work in Progress Session, IEEE Real-Time Systems Symposium (RTSS 2016). 29, Nov to 2, Dec, 2016. Porto, Portugal.Real-time systems are becoming more complex and open, thus increasing their development and verification costs. Although several static verification tools have been proposed over the last decades, they suffer from scalability and precision problems. As a result, the tools fail to cover all the necessary safety properties for realistic real-time applications involving a large number of components and tasks. Runtime verification is a formal technique that verifies properties during system execution with the support of monitors. The monitors are generated from formal languages using correct-by-construction generation methods. Runtime verification can thus be used as a complement or replacement for static verification approaches. The current state-of-the-art tools either do not have notion of time, or suffer from the potential blowup of states at run-time. In this paper, we propose REVERT, a framework developed with a focus on the verification of functional and non-functional properties with timing constraints. The contribution of this work is twofold: (i) a domain-specific specification language allowing the definition of requirements for real-time applications; (ii) a novel mechanism to generate monitors, with state-space and time guarantees, capable of identifying and reacting to timing properties defined with the proposed specification language.info:eu-repo/semantics/publishedVersio

Semi-automatic Architectural Suggestions for the Functional Safety of Cooperative Driving Systems

In cooperative driving, vehicles coordinate their actions as part of a system. Cooperative driving capabilities in vehicles are achieved by means of software, making this software safety critical. The current safety standard for vehicles, ISO 26262, is designed for individual vehicles and their software architecture, but not for cooperative driving settings. Moreover, the guidelines from the standard can only be used for generating safety goals and checking adherence to them. The standard's guidelines do not cover mechanisms to meet the unmet safety goals or provide designers with available architecture choices.This paper presents an extension of the ISO 26262 standard from a single vehicle setting to a cooperative vehicle setting. We also show that the use of safety tactics and design patterns, which enable designers to be aware of possible design choices, can seamlessly be integrated into the ISO 26262 process. The resulting methodology enables designers to make informed choices and cover safety goals. Our case study on the software architecture of a real-life cooperative driving prototype shows that the proposed approach can provide new insights about its safety and mechanisms to improve it

Summary: A functional safety assessment method for cooperative automotive architecture

The scope of automotive functions has grown from a single vehicle as an entity to multiple vehicles working together as an entity, referred to as cooperative driving. The current automotive safety standard, ISO 26262, is designed for single vehicles. With the increasing number of cooperative driving capable vehicles on the road, it is imperative to systematically assess their architectures’ functional safety. Many methods are proposed to assess architectures with respect to different quality attributes in the software architecture domain, but to the best of our knowledge, functional safety assessment of automotive architectures is not explored in the literature. We present a method leveraging existing software architecture and safety engineering research, to check whether the functional safety requirements for cooperative driving scenarios are fulfilled in the technical architecture of a vehicle. We apply our method on a real-life academic prototype for a scenario—platooning—and discuss our insights

A functional safety assessment method for cooperative automotive architecture

The scope of automotive functions has grown from a single vehicle as an entity to multiple vehicles working together as an entity, referred to as cooperative driving. The current automotive safety standard, ISO 26262, is designed for single vehicles. With the increasing number of cooperative driving capable vehicles on the road, it is now imperative to systematically assess the functional safety of architectures of these vehicles. Many methods are proposed to assess architectures with respect to different quality attributes in the software architecture domain, but to the best of our knowledge, functional safety assessment of automotive architectures is not explored in the literature. We present a method, that leverages existing research in software architecture and safety engineering domains, to check whether the functional safety requirements for a cooperative driving scenario are fulfilled in the technical architecture of a vehicle. We apply our method on a real-life academic prototype for a cooperative driving scenario, platooning, and discuss our insights